EMERGENCY OPERATION FOR CROSS CARRIER SIGNALING IN MULTI-CARRIER OPERATION

专利摘要:
emergency operation for cross-carrier signaling in multi-carrier operation. techniques to support restore operation in a multi-carrier communication system are described. in one aspect, a UE may determine at least a first downlink control information (dci) format for monitoring a first carrier. the eu can monitor the first dci format(s) on the first carrier to detect dci sent to the eu. the UE can receive a reconfiguration message related to communication on a plurality of carriers by the UE with the cross-carrier signaling, and can determine at least a second dci format to monitor on the first carrier based on the reconfiguration message. the u can monitor the first dci format(s) and the second dci format(s) on the first carrier after receiving the reset message.
公开号:BR112012015950B1
申请号:R112012015950-0
申请日:2010-12-23
公开日:2021-06-15
发明作者:Jelena M. Damnjanovic；Juan Montojo；Aleksandar Damnjanovic；Peter Gaal
申请人:Qualcomm Incorporated；
IPC主号:

专利说明:

[0001] This application claims the benefit of US Provisional Order No. 61/290,724, entitled "RESTORATION OPERATION IN CROSS-CARRIER SIGNALING BASED MULTICARRIER OPERATION IN LTE-A", filed on December 29, 2009, and US Provisional Order No. 61/313,647, entitled "METHOD AND APPARATUS THAT FACILITATES CROSS-CARRIER SIGNALING BASED MULTICARRIER OPERATION IN LONG TERM EVOLUTION SYSTEMS", filed on March 12, 2010, both are assigned to the assignee of this instrument and incorporated herein by reference. Field of Invention
[0002] The present disclosure relates generally to communication, and more specifically to techniques to support communication in a wireless communication system. Description of Prior Art
[0003] Wireless communication systems are widely used to provide various communication contents, such as voice, data, video, messages, broadcast, etc. These wireless systems can be multiple access systems capable of supporting multiple users sharing available system resources. Examples of such multiple access systems include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, orthogonal FDMA systems (OFDMA) , and single-carrier FDMA (SC-FDMA) systems.
[0004] A wireless communication system can include a number of base stations that can support communication to a number of user equipment (UES). A UE can communicate with a base station via downlink and uplink. The downlink (or forward link) refers to the communication link from the base station to the UE, and the uplink (or reverse link) refers to the communication link from the UE to the base station. Invention Summary
[0005] Techniques to support restore operation in a multi-carrier communication system are disclosed. The UE can operate on multiple carriers of multicarrier operation. Cross-carrier signaling can be used for multi-carrier operation and can entail sending control information over one carrier to support data transmission on another carrier. Restore operation refers to the ability to reliably send control information to the same UE when a mode of operation of the UE (for example, whether the UE is operating with a single carrier or multiple carriers) is unknown.
[0006] In a design, a UE may determine at least a first downlink control information (DCI) format to monitor on a first carrier. The UE may monitor the at least one first format of DCI on the first carrier to detect DCI sent to the UE. The UE may receive a reconfiguration message related to communication on a plurality of carriers by the UE with the cross-carrier signaling. The UE may determine at least a second DCI format to monitor on the first carrier based on the reset message. The UE may monitor the at least one first DCI format and the at least one second DCI format on the first carrier after receiving the reconfiguration message to detect DCI sent to the UE. Restore operation is supported by having UE monitoring for at least one first DCI format before and after receiving the reset message. DCI can be reliably sent to the UE based on the at least one first DCI format, even when there is uncertainty as to a UE mode of operation.
[0007] In a design, a base station can determine the at least one first DCI format monitored by the UE on the first carrier. The base station may send DCI over the first carrier to the UE based on the at least one first DCI format. The base station can send the reconfiguration message related to communication on the plurality of carriers by the UE with the cross-carrier signaling. The base station may determine the at least one second DCI format monitored by the UE on the first carrier in response to the reconfiguration message. The base station may send DCI on the first carrier to the UE based on the at least one first DCI format and the at least one second DCI format after sending the reconfiguration message.
[0008] In one design, each second DCI format may comprise a corresponding first DCI format and at least one additional field to support cross-carrier signaling. The at least one additional field may include a cross-carrier indicator (CIF) field, as described below. The at least one first DCI format can have a first size, and the at least one second DCI format can have a second size that is different from the first size.
[0009] Restore operation can be restricted in various ways in order to limit the number of blind decodings performed by UE to detect DCI sent to UE. In a project, restore operation may be supported for certain DCI formats but not other DCI formats. In another design, restore operation may be supported by one or more carriers, but not other carriers. In yet another design, restore operation may be supported by one or more UE search spaces but not other search spaces. In yet another design, restore operation may be supported by certain Physical Downlink Control Channel (PDCCH) candidates for the UE, but not other PDCCH candidates. Restore operation can also be restricted in other ways. Various aspects and features of the disclosure are described in detail below. Brief Description of Figures
[00010] Figure 1 - shows an exemplary wireless communication system.
[00011] Figure 2 - shows an exemplary frame structure.
[00012] Figure 3A - shows an example of a single-carrier operation.
[00013] Figures 3B and 3C - are examples of multicarrier operation without and with cross-carrier signaling, respectively.
[00014] Figure 4 - shows two exemplary DCI formats.
[00015] Figure 5A - shows the reconfiguration of a different downlink transmission mode.
[00016] Figure 5B - shows multi-carrier operation reconfiguration with cross-carrier signaling.
[00017] Figure 6 - shows an exemplary restore operation when a new carrier is added.
[00018] Figure 7 - shows an exemplary restore operation when cross-carrier signaling is enabled.
[00019] Figure 8 - shows an exemplary restore operation during a transition interval to reset.
[00020] Figure 9 - shows a block diagram of an exemplary message generator at a base station.
[00021] Figure 10 - shows a block diagram of an exemplary message detector in a UE.
[00022] Figure 11 - shows an exemplary process for receiving DCI by a UE.
[00023] Figure 12 - shows an exemplary process for sending DCI by a base station.
[00024] Figure 13 - shows an exemplary block diagram of a base station and a UE. Detailed Description of the Invention
[00025] The techniques described herein can be used for various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes broadband CDMA (WCDMA) and other variants of CDMA. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. A TDMA system can implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA system can implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Wideband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM®, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). Long Term Evolution 3GPP (LTE) and LTE-Advanced (LTE-A) are the new UMTS releases that use E-UTRA, which employs OFDMA on the downlink and SC-FDMA on the uplink. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization called The '3rd Generation Partnership Project' (3GPP). cdma2000 and UMB are described in documents from an organization called The '3rd Generation Partnership Project' 3rd Generation Partnership 2" (3GPP2). The techniques described here can be used for the aforementioned radio systems and technologies, as well as other radio systems and technologies. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.
[00026] Figure 1 shows a wireless communication system 100, which can be an LTE system or some other system. System 100 may include an evolved number of UE nodes (eNBs) 110 and other network entities. An eNB can be an entity that communicates with the UEs and can also be referred to as a base station, a node B, an access point, etc. Each eNB 110 can provide communication coverage for a certain geographic area and can support communication for UEs located within the coverage area. To improve system capacity, the overall coverage area of an eNB can be divided into multiple (eg three) smaller areas. Each smaller area can be served by a respective eNB subsystem. In 3GPP, the term "cell" can refer to the smallest coverage area of an eNB and/or an eNB subsystem serving this coverage area.
[00027] A network controller 130 can couple to a set of eNBs and can provide coordination and control for these eNBs. Network controller 130 may comprise a Mobility Management Entity (MME) and/or some other network entity.
[00028] The UEs 120 can be dispersed throughout the system, and each UE can be stationary or mobile. A UE may also be referred to as a mobile station, a terminal, an access terminal, a subscriber unit, a station, etc. A UE can be a cellular phone, a personal digital assistant (PDA), a modem, a wireless communication device, a handheld device, a laptop computer, a cordless telephone, a wireless local loop station (WLL), a smart phone, a netbook, a smartbook, etc.
[00029] Figure 2 shows a frame structure 200 for frequency division duplexing (FDD) in LTE. For FDD, the downlink and uplink can be assigned different frequency channels. The transmission timeline for each of the downlink and uplink can be divided into radio frame units. Each radio frame can have a predetermined duration (e.g., 10 milliseconds (ms)) and can be divided into 10 subframes with indices from 0 to 9. Each subframe can include two partitions. Each radio frame can thus have 20 partitions with indices from 0 to 19. Each partition may include seven symbol periods for a normal cyclic prefix (as shown in Figure 2) or six symbol periods for an extended cyclic prefix.
[00030] Each subframe for the downlink may include a control region and a data region, which may be time division multiplexed (TDM), as shown in figure 2. The control region may include the first M periods of subframe symbol, where M can equal 1, 2, 3 or 4 and can change from subframe to subframe. The control region can carry control information for UEs. The data region may include the remaining symbol periods of the subframe and may carry data and/or other information for UEs.
[00031] Each subframe for the uplink can include a control region and a data region, which can be frequency division multiplexed (FDM) (not shown). The control region can be formed at both edges of the system bandwidth and can have a configurable size, which can be selected based on the amount of control information to be sent uplink by the UEs. The data region can include the remaining frequency not covered by the control region.
[00032] An eNB may send downlink control information (DCI) over a Physical Downlink Control Channel (PDCCH) in the control region of a subframe to the downlink (or a downlink subframe). The DCI may comprise downlink grants (DL), uplink grants (UL), power control information, etc. The eNB may send data on a Physical Downlink Shared Channel (PDSCH) in the data region of the downlink subframe. The PDSCH may carry data to UEs scheduled for transmission of downlink data and/or other information.
[00033] A UE may send uplink control information (UCI) on Physical Uplink Control Channel (PUCCH) in allocated resource blocks in the control region of a subframe to the uplink (or an uplink subframe ). The UCI may include acknowledgment information (ACK) for data transmission sent on the downlink, quality indicator channel information (CQI), scheduling request, etc. The UE may send only data, or both data and UCI, on Physical Uplink Shared Channel (PUSCH) in allocated resource blocks in the data region of the uplink subframe. An uplink transmission can span both partitions of a subframe and can skip across frequency.
[00034] The system can support operation on a single carrier or multiple carriers for each of the downlink and uplink. A carrier can refer to a range of frequencies used for communication and can be associated with certain characteristics. For example, each bearer may be assignable to one or more UEs for communication. A carrier can also be referred to as a component carrier, a cell, a frequency, an RF channel, etc. Multi-carrier operation may also be referred to as carrier aggregation or multi-carrier operation. A UE may operate on one or more downlink carriers (or downlink carriers) and one or more uplink carriers (or uplink carriers) for communication with an eNB. The eNB may send the data and DCI on one or more downlink carriers to the UE. The UE may send data and UCI on one or more uplink carriers to the eNB.
[00035] Figure 3A shows an example of a single-carrier operation by a UE. As illustrated, the UE may operate on a single downlink carrier (DL) and a single uplink carrier (UL) for communication with an eNB. The eNB may send a DL grant and/or an UL grant to the UE on the PDCCH in the control region of a downlink subframe. The DL grant may comprise several parameters for a downlink data transmission from the eNB to the UE. The UL grant may comprise several parameters for an uplink data transmission from the UE to the eNB. The eNB may send the downlink data transmission to the UE on the PDSCH in the data region of the downlink subframe. The UE may send the uplink data transmission to the eNB in the PUSCH in the data region of an uplink subframe.
[00036] Fig. 3B shows an example of multi-carrier operation without cross-carrier signaling by a UE. Here, the UE can operate on the 'K' DL carriers and 'L' UL carriers for communication with an eNB, where K may or may not equal L. Each UL carrier can be paired with a DL carrier. Control information to support data transmission on a given DL carrier may be sent on that DL carrier and/or an associated UL carrier. Likewise, control information to support data transmission on a given UL carrier may be sent on that UL carrier and/or associated DL carrier.
[00037] Cross-carrier signaling refers to sending control information on one carrier to support the transmission of data on another carrier. For example, a DL grant can be sent on one DL carrier to support data transmission on another DL carrier. In a cross-carrier signaling design, one carrier can be designed as a primary carrier for each of the downlink and uplink, and the remaining carriers can be referred to as extension carriers. The main carrier may also be referred to as an anchor carrier, a base carrier, etc. An extension carrier may also be referred to as a regular carrier, a secondary carrier, etc. A UE may be configured to operate on the primary carrier and zero or more extension carriers for each of the downlink and uplink.
[00038] Fig. 3C shows an example of multi-carrier operation with cross-carrier signaling by a UE. In the example shown in Fig. 3C, DL carrier 1 can be a primary DL carrier for the UE, and the UL carrier 1 can be a primary UL carrier for the UE. An eNB may send DCI (e.g., DL and UL grants) to the UE on the primary DL carrier to support data transmission on all DL and UL carriers. The UE may send UCIs to the eNB on the UL primary carrier to support data transmission on all DL and UL carriers.
[00039] Figure 3C shows a design to support cross-carrier signaling for multi-carrier operation using primary DL and UL carriers. Cross-carrier signaling may also be supported in other ways. In general, cross-carrier signaling can be supported in any way that can send control information on one carrier to support data transmission on another carrier. For clarity, and not as a limitation of disclosure, most of the description below assumes the design shown in Figure 3C, with DCI being sent over the primary DL carrier and UCI being sent over the primary UL carrier to support cross-carrier signaling .
[00040] System 100 can support a number of DCI formats that can be used to send DCI on the downlink. Table 1 presents a set of DCI formats that may be supported by the system. DCI format 0 can be used to send UL grants for uplink data transmission. DCI formats 1, 1A, 1B, 1C and 1D can be used to send DL grants for data transmission of a codeword on the downlink. A codeword can correspond to a transport block or a packet. DCI formats 2, 2A and 2B can be used to send DL grants for data transmission of two codewords downlink for multiple input and multiple output (MIMO). DCI 3 and 3A formats can be used to send transmit power control (TPC) information to UEs. DCI formats 0, 1A, 3 and 3A are the same size. DCI formats 1, 1B, 1C, 1D, 2, 2A and 2B can be different sizes.


[00041] Table 1 lists the DCI formats supported by LTE Version 9. Other DCI formats may also be supported, for example, in future LTE versions. In addition, a set of DCI formats can be defined to support cross-carrier signaling. In one design, a DCI format that supports cross-carrier signaling may include (i) all fields of a corresponding DCI format that does not support cross-carrier signaling (for example, one of the DCI formats shown in Table 1) and (ii) one or more additional fields to support cross-carrier signaling. In one design, cross-carrier signaling may be supported by a cross-carrier indicator field (CIF) that indicates a carrier on which a data transmission is scheduled. The CIF can have one or more of the following characteristics:• CIF presence can be semi-statically enabled, eg, upper layer signaling pathway,• setting for CIF presence can be UE-specific,• CIF (if configured) can be a fixed-length field (eg, three-bit to support up to eight carriers),• The location of the CIF (if configured) can be fixed for all DCI formats, regardless of their sizes,• Cross-carrier can be configured for both DCI formats for the UE which is the same size or different sizes: • There may be an upper limit on the total number of blind decodings by the UE.
[00042] Figure 4 shows a DCI X format that does not support cross-carrier signaling. The DCI X format can match any of the DCI formats shown in Table 1 and can include various fields used to send the different types of information. For example, DCI X format can be used for a grant and can include fields to carry resources allocated for data transmission, a modulation and coding scheme (MCS), precoding information, HARQ information, a TPC command, and/or other information.
[00043] Figure 4 also shows a design of a DCI X’ format that supports cross-carrier signaling. In this project, the DCI X’ format includes all fields in DCI X format and an additional field for the CIF. Because of the additional CIF, the DCI X’ format is a different size than the corresponding DCI X format.
[00044] In general, CIF can be added to any of the DCI formats shown in Table 1 to form a DCI format that supports cross-carrier signaling. For example, CIF can be added to DCI Formats 1A, 0, and 2 to form DCI formats 1A', 0', and 2', respectively. For clarity, in the present description, a format that DCI does not support cross-carrier signaling may be denoted without a prime (e.g., DCI X format, where X may be any suitable design). A DCI format that supports cross-carrier signaling may be denoted with a prime (for example, DCI X’ format). The DCI X' Format may include all fields in the DCI X format and the CIF and/or other fields to support cross-carrier signaling.
[00045] In LTE Version 8 (Rel-8) and LTE Version 9 (Rel-9), the UE can be statically semi-configured by Radio Resource Control (RRC) with one of eight 1A downlink transmission modes 8. For each downlink transmission mode, the UE can control two DCI formats: 1A DCI format and a mode dependent DCI format. For example, the UE can monitor DCI format 1A as well as DCI format 2 for downlink transmission mode 4 for closed loop spatial multiplexing. For all downlink transmission modes, the UE can also monitor DCI 0 format used for uplink scheduling.
[00046] An eNB can send DCI to the UE on the PDCCH using any of the DCI formats supported by the UE. The eNB can also send DCI on the PDCCH in 1, 2, 4 or 8 control channel elements (CCES), which correspond to an aggregation level of 1, 2, 4 or 8, respectively. Each CCE can include nine resource elements, with each resource element spanning a subcarrier in a symbol period. Different levels of aggregation can be used for different levels of protection for the DCI. The eNB can send DCI to the UE only in certain CCEs, which can be located in a common search space and a UE-specific search space for the UE. The common search space can be applicable to all UEs while the UE-specific search space can be specific to the UE. The UE may have a number of PDCCH candidates in the common search space and the UE-specific search space. Each PDCCH candidate can correspond to a specific set of CCEs in which DCI can be sent to the UE. Table 2 lists the PDCCH candidates monitored by the UE for different levels of aggregation in the common and UE-specific search spaces.


[00047] For each PDCCH candidate, the UE can perform blind decoding for each DCI size supported by the UE. The DCI size determines the number of bits of information to send, which in turn affects the code rate. The total number of blind decodes can then be dependent on the number of PDCCH candidates and the number of DCI sizes supported by the UE. A blind decoding can also be referred to as a decoding candidate.
[00048] DCI formats 1A and 0 are the same size. Thus, for any downlink transmission mode, there can be only two DCI sizes for unicast transmissions from DCI to UE: one DCI size for DCI formats 1A and 0, and another DCI size for a DCI format. Mode dependent DCI. The UE can perform 22 blind decodes for the 22 PDCCH candidates in Table 2 for each of the two DCI sizes, or a total of 44 blind decodes.
[00049] DCI formats 1A and 0 can be used for all downlink transmission modes and carrier configurations. This allows the eNB to have a DCI format for each link (downlink and uplink) that the eNB can use to send DCI to the UE in any subframe regardless of the RRC configuration and reconfiguration of the UE. This project may counter a potential ambiguous duration when the UE is under RRC reconfiguration, as described below.
[00050] Fig. 5A shows an example of RRC reconfiguration for a different mode of downlink transmission. Before time T1, a UE operates on the basis of downlink transmission mode U and supports DCI formats 1A and 0 and a mode dependent DCI format W. At time T1, RRC reconfiguration is performed (e.g., via the sending an RRC connection reconfiguration message from an eNB to the UE) to change the downlink transmission mode of the UE from the U mode to the V mode. At time T2, the UE can operate based on the mode of downlink transmission V and can support DCI formats 1A and 0 and a Z-mode dependent DCI format. The transition interval from time T1 to time T2 can be indeterminate (provided that in LTE there is no action time" in which new downlink transmission mode V becomes effective.) The eNB may not know the status of the UE and the particular downlink transmission mode supported by the UE during the RRC reconfiguration period. send DCI to UE using DCI formats 1A and 0, which are assumed rted by the UE, both before and after the RRC reconfiguration. The use of DCI formats 1A and 0 for all downlink transmission modes can thus allow eNB-UE communication without interruption during the transition interval.
[00051] Fig. 5B shows an example of RC reconfiguration for multi-carrier operation with cross-carrier signaling. Before time T1, a UE operates on one or multiple carriers and does not support cross-carrier signaling, which may be referred to as a "non-CIF" mode. The UE supports DCI formats 1A and 0 and a mode dependent DCI format W before time T1. At time T1, RRC reconfiguration is performed to change the operation of the UE to support cross-carrier signaling, which may be referred to as a "CIF" mode. At the time of T2, the UE operates with cross-carrier signaling and supports DCI formats 1A' and 0' and a mode dependent on the DCI W format.
[00052] As shown in Figure 5B, when the UE is semi-statically reconfigured from non-CIF to CIF (or vice versa), there is no longer a common DCI format (before and after RRC reconfiguration) per link to allow that the eNB reliably send DCI to the UE. This can result in the loss of DCI in the UE, which can degrade performance. For example, at time T3 within transition interval T1-T2 (not shown in Fig. 5B), the eNB can assume that the UE has switched to CIF mode and can send a DL grant based on DCI format 1A'. However, UE can still operate in non-CIF mode at time T3 and can perform blind decoding based on DCI format 1A. In that situation, the UE could lose the DL grant sent by the eNB and also lose the downlink data transmission sent based on the DL grant.
[00053] In one aspect, restoration operation can be supported by cross-carrier signaling in multi-carrier operation so that an eNB can reliably can send DCI to a UE. Restore operation can be supported by maintaining at least one common DCI format for each link before and after RRC reconfiguration, for example, to enable or disable cross-carrier signaling.
[00054] In a design, the following can be assumed by cross-carrier signaling: • a UE can be configured with cross-carrier (or CIF) signaling only if the UE is configured with two or more carriers, and• The reset of CIF and the number of carriers for the UE is semi-static. DCI formats that support cross-carrier signaling (eg DCI formats with CIF) and DCI formats that do not support cross-carrier signaling (eg DCI formats without CIF) may have different sizes. Thus, a UE can perform two blind decodings for two DCI formats, with and without CIF, for each PDCCH candidate. The total number of blind decodings to be performed by the UE can increase substantially in order to support restoration operation for cross-carrier signaling. In one design, restoration operation can be supported on only a subset of all carriers. A carrier on which restore operation is supported can be referred to as a restore carrier. A carrier on which restore operation is not supported can be referred to as a non-restore carrier. For each non-restoration bearer, a UE can perform blind decoding of DCI formats with and without CIF. For each non-restoration carrier, UE can perform blind decoding of only DCI formats with CIF. This can reduce the number of blind decoding for non-restoring carriers. Figure 6 shows a design that supports restore operation when a new carrier is added and cross-carrier signaling is enabled. In the example shown in Figure 6, before time T1, a UE operates on carrier 1 and supports DCI formats 1A and 0 and a mode dependent DCI format W. At time T1, RRC reconfiguration is performed to add another carrier 2 and to enable cross-carrier signaling for the UE. At time T2, the UE operates on carriers 1 and 2 with cross-carrier signaling. In a first design, the UE supports restoration operation on carrier 1 and does not support restoration on carrier 2, as shown in figure 6. In this project, in T2 time, the UE can support the following: • Carrier 1 - DCI formats 1A' and 0' (with CIF), DCI formats 1A and 0 (without CIF), and DCI W format (with CIF, for mode of downlink transmission supported by the UE on carrier 1), e• Carrier 2 - DCI formats 1A' and 0' (with CIF) and DCI Z' format (with CIF, for the downlink transmission mode supported by the EU on carrier 2).
[00055] In a second project, the UE can support restore operation on both carriers 1 and 2. In this project, at time T2, the UE can support the following: • Carrier 1 - DCI formats 1A' and 0', 1A and 0, and W, e• Carrier 2 - DCI formats 1A' and 0', 1A and 0, and Z'.
[00056] Figure 7 shows a design to support the restore operation when cross-carrier signaling is enabled. In the example shown in Fig. 7 before time T1, the UE operates on two carriers 1 and 2 without cross-carrier signaling. The UE supports DCI formats 1A and 0 and a mode dependent DCI format W on carrier 1 and further supports DCI formats 1A and 0 and a mode dependent DCI format Z on carrier 2. At time T1, the reconfiguration RRC is performed to enable cross-carrier signaling for the UE. At time T2, the UE operates on carriers 1 and 2 with cross-carrier signaling.
[00057] In a first project, the UE supports restore operation on carrier 1 and does not support restore operation on carrier 2, as shown in figure 7. In this project, at time T2, the UE can support the following:• Carrier 1 - DCI formats 1A' and 0', 1A and 0, and W, e• Carrier 2 - DCI formats 1A' and 0' and Z'.
[00058] In a second design, the UE supports restore operation on both carriers 1 and 2. The UE can then support DCI formats 1A' and 0', 1A and 0, and Z' on carrier 2.
[00059] In general, the restore operation can be supported on any number of carriers, which can be semi-statically reconfigured for the UE. For example, restore operation may be supported only on the primary carrier, or the primary carrier and one or more other carriers, or some other carrier or combination of carriers. The restoration bearer(s) can be explicitly or implicitly configured such that both the eNB and the UE are aware of the restoration bearer(s). In one design, both DCI formats 1A and 0 can be supported on each restore carrier, so that DCI can be reliably sent to control data transmission on downlink and uplink.
[00060] In a project, restore operation can be supported by only a subset of all PDCCH candidates, in order to limit the number of blind decodings by a UE. The UE can perform three blind decodings for three DCI sizes for each PDCCH candidate - a first blind decoding for DCI formats 1A and 0, a second blind decoding for a mode dependent DCI format, and a third blind decoding for the 1A' and 0' DCI formats. The UE can then perform a total of 66 blind decodes for three DCI sizes for one carrier. The total number of blind decodes can be reduced by placing certain restrictions on how DCI can be sent to the UE. These restrictions should minimally affect performance as the restore operation for RRC reset can be a frequent event. Several models for reducing the number of blind decodings are described below.
[00061] In a first project to reduce the number of blind decodings, DCI formats with and without CIF can be supported in different search spaces. Each search space can support both DCI formats with CIF or DCI formats without CIF. In a project, DCI formats without CIF (eg DCI Formats 1A and 0) can be supported in the common search space, and DCI formats with CIF (eg DCI Formats 1A', 0' and W) can be supported in the UE-specific search space as shown in Table 3. DCI can be sent as unicast to a specific UE in the common or UE-specific search space using 1A, 0, 1A', 0' or DCI format W. The unicast DCI can be scrambled with a temporary UE-specific radio network identifier (RNTI), such as a cell RNTI (C-RNTI), a semi-persistent scheduling (SPS) C-RNTI, a temporary C-RNTI , etc. DCI can be sent as broadcast to all UEs in the common search space using DCI 1A or 1C format. The broadcast DCI can be scrambled with an RNTI known to all UEs, such as an RNTI information system (SI-RNTI), a Paging RNTI (P-RNTI), a random access RNTI (RA-RNTI), etc. DCI for TPC information can be sent via DCI format 3 or 3A in the common search space and can be scrambled with an RNTI TPC-PUCCH or an RNTI TPC-PUSCH, which are known by the UEs.


[00062] With the design shown in Table 3, a UE can have two DCI sizes for the common search space and two DCI sizes for the UE-specific search space. The two DCI sizes for the common search space can include one DCI size for DCI Formats 1A, 0, 3, and 3A and another DCI size for DCI Format 1C. The two DCI sizes for the UE-specific search space can include one DCI size for DCI Formats 1A' and 0' and another DCI size for DCI W format. For the design shown in Table 3, the UE can perform the same number of link decodes (e.g. 44) to support the restoration operation with the cross-carrier signaling as another UE that does not support this restoration operation.
[00063] The design in Table 3 may have no impact on the scheduling of a UE for (i) downlink data transmission on the same DL carrier on which the DCI is sent and (ii) uplink data transmission into a UL carrier associated with this DL carrier. In these cases, the CIF is not required. DL and UL grants can be sent to the UE in (i) the common search space using DCI formats 1A and 0 or (ii) the UE specific search space using DCI formats 1A' and 0'. The UE may be scheduled in both the UE-specific and common search spaces for data transmission on downlink and uplink.
[00064] Due to search space constraints, the design shown in Table 3 may have some impact on scheduling a UE to (i) transmit downlink data on a DL carrier other than the DL carrier on which DCI is sent and (ii) uplink data transmission on an UL carrier not associated with the DL carrier on which DCI is sent. In these cases, the CIF field can be used to indicate the DL or UL carrier on which data transmission is scheduled. The DL and UL grants can be sent to the UE in the UE-specific search space using DCI formats 1A' and 0' and not in the common search space.
[00065] In a second project to reduce the number of blind decodings, DCI formats with and without CIF can be supported in a subset of the search spaces. In a project, DCI formats without CIF (eg DCI formats 1A and 0) and some DCI formats with CIF (eg DCI formats 1A' and 0') may be supported in the common search space, such as shown in Table 4. DCI formats with CIF (eg DCI formats 1A', 0' and W) can be supported in the UE-specific search space, as also shown in Table 4.


[00066] The design shown in Table 4 can alleviate some scheduling constraints imposed by the design shown in Table 3. In particular, DL and UL grants can be sent to a UE in both the common and UE-specific search spaces using the 1A' and 0' DCI formats. The UE can perform more blind decodings in the common search space to support the DCI formats with and without CIF.
[00067] For the design shown in Table 4, both DCI 1A format and DCI 1A format' with the CIF set set to '000' (by cross-carrier referring to the same DL carrier) can be used in the search space It is common to send a DL grant on a DL carrier to schedule a UE to transmit data on the same DL carrier. Support DCI 1A format as well as DCI 1A format’ with CIF set set to '000' is doubled. Thus, 1A' and 0' DCI formats with the CIF set to '000' can be avoided in the common search space, and 1A and 0 DCI formats can be used instead.
[00068] In a third project to reduce the number of blind decodings, restore operation cannot be supported on certain carriers. In one design, DCI formats with CIF (eg DCI formats 1A', 0' and W) can be supported in both common and UE-specific search spaces for a non-restoration carrier, as shown in Table 5. DCI can be sent as unicast to a specific UE in the common search space, or UE-Specific using the 1A', 0' or W DCI format. DCI can be sent as a message to all UEs in the common search space using DCI 1A or 1C format. DCI to TPC information can be sent using DCI 3 or 3A format in the common search space. Table 5 - Non-Restore Carrier Search Space Partitioning

[00069] In a fourth project to reduce the number of blind decodings, DCI formats with and without CIF can be supported by different sets of PDCCH candidates. As shown in Table 2, there are two aggregation levels of 4 and 8 in the common search space, with aggregation level 4 including 4 PDCCH candidates and aggregation level 8 including 2 PDCCH candidates. As also shown in Table 2, there are four aggregation levels of 1, 2, 4 and 8 in the UE-specific search space, with aggregation level 1 including 6 PDCCH candidates, aggregation level 2 including 6 PDCCH candidates, aggregation level 4 including 2 PDCCH candidates and aggregation level 8 including 2 PDCCH candidates. In a project, for a level of data aggregation in a given search space, DCI formats without CIF may be allowed for some PDCCH candidates and DCI formats with CIF may be allowed for the remaining PDCCH candidates. As an example, for aggregation level 4 in the common search space, DCI formats 1A and 0 can be allowed for the first two PDCCH candidates, and DCI formats 1A' and 0' can be allowed for the last two candidates of PDCCH. As another example, for aggregation level 8 in the common search space, DCI formats 1A and 0 can be allowed for the first PDCCH candidate, and DCI formats 1A' and 0' can be allowed for the other PDCCH candidate .
[00070] In general, each level of aggregation in each search space can support only DCI formats without CIF, or only DCI formats with CIF, or both. If a given level of aggregation in a given search space supports the DCI formats with and without CIF, then any number of PDCCH candidates can support the DCI formats without CIF, and any number of PDCCH candidates can support the formats of DCI without CIF. Furthermore, a given PDCCH candidate can support only DCI formats without CIF, or only DCI formats with CIF, or both. Aggregation levels in the common and UE-specific search spaces can be defined in several ways. For example, each aggregation level in the common search space can support the DCI formats with and without CIF while each aggregation level in the UE-specific search space can support only the DCI formats with CIF.
[00071] Other projects to reduce the number of blind decodings can also be implemented. Any or any combination of these designs can be implemented to reduce the number of blind decodings.
[00072] In general, to reduce the number of blind decodings, restore operation can be supported:• Only on one or more carriers, instead of all carriers,• Only on common search space or specific search space of UE on a carrier, • Only at one or more designated aggregation levels, and/or • Only for a subset of PDCCH candidates.
[00073] In one project, a first set of PDCCH candidates can support DCI formats without CIF, and a second set of PDCCH candidates can support DCI formats with CIF. In a project, the first set can be non-overlapping with the second set, so each PDCCH candidate can be included in only one set. In another design, the first set can be overlaid with the second set so that one or more PDCCH candidates can be included in both sets.
[00074] The first and second sets of PDCCH candidates can be defined in various ways. In one project, the first set might include PDCCH candidates in one search space, and the second set might include PDCCH candidates in another search space, for example, as shown in Table 3. In another project, the first set may include PDCCH candidates for some levels of aggregation, and the second set may include PDCCH candidates for other levels of aggregation. In yet another design, the first set may include some PDCCH candidates at a given aggregation level or a given search space, and the second set may include other PDCCH candidates at a given aggregation level or search space. The first and second sets can also be defined in other ways, based on search space, level of aggregation, etc., to obtain the desired total number of blind decodings and the desired scheduling flexibility for the UEs.
[00075] In another aspect, a transition monitoring mode can be defined in which a UE skips monitoring a mode dependent DCI format during reconfiguration from non-CIF mode to CIF mode, or vice versa, to in order to reduce the number of blind decoding. During the transition interval, the UE can support DCI formats 1A and 0 without CIF and DCI formats 1A' and 0' with CIF in order to support the restore operation. However, the UE cannot support a mode dependent DCI format during the transition interval. The UE can then perform blind decoding for only two DCI sizes during the transition interval.
[00076] For clarity, the description below assumes the case of reconfiguration to enable cross-carrier signaling. However, the models described below can apply equally to the reconfiguration case to disable cross-carrier signaling over the downlink, and also to the reconfiguration cases for uplink carriers.
[00077] Figure 8 shows a design to support restore operation during a transition interval to reset to enable cross-carrier signaling. In the example shown in Figure 8, before time T1, a UE supports DCI formats 1A and 0 and a mode dependent DCI format W. At time T1, RRC reconfiguration is performed to enable cross-carrier signaling and possibly changing a downlink transmission mode for the UE. At time T2, the UE operates with cross-carrier signaling and supports DCI formats 1A and 0 without CIF and DCI formats 1A' and 0' with CIF. The UE also supports either a mode dependent DCI format Z' with CIF for a new downlink transmission mode (as shown in Fig. 8) or a mode dependent DCI format W' with CIF for the transmission mode of old downlink (not shown in figure 8).
[00078] During the transition interval from time T1 to time T2, the UE monitors DCI Formats 1A and 0 without CIF and DCI formats 1A’ and 0' with CIF. UE skip monitor mode dependent DCI format during transition interval. The UE can perform blind decoding for only two DCI sizes during the transition interval.
[00079] Mode dependent DCI format is generally used to support a higher data rate. Resetting can be a rare event, and the transition interval can be relatively short. As a result, there can be negligible performance impact due to the UE not monitoring mode dependent DCI format during the transition interval.
[00080] In a design, transition monitoring mode can be applicable to only a subset of all carriers configured for the UE (for example, only for the primary carrier). In another design, transition monitoring mode can be applicable to all restore carriers. The transition monitoring mode may not be applicable if the UE is only configured with one carrier or if there is no restore carrier.
[00081] Transition monitoring mode can also be restricted in other ways. In a project, transition monitoring mode can be applicable for the UE-specific search space, but not the common search space. In this design, the UE can monitor DCI formats 1A and 0 and a mode dependent DCI format (eg with or without CIF) in the common search space during the transition interval.
[00082] The transition interval can be defined in several ways and can be defined in different ways for an eNB and a UE involved in the reconfiguration. In a design, for the eNB, the transition interval can start when the eNB starts a CIF-related RRC Reconfiguration Procedure, which can be when an RRCConnectionReconfiguration message is sent by the eNB. The transition interval may end when the RRC reconfiguration procedure completes, which may be when an RRCConnectionReconfigurationComplete message is received by the eNB.
[00083] In a design, for the UE, the transition interval can start when the UE becomes aware of the CIF-related RRC reconfiguration process, which can be when the RRCConnectionReconfiguration message is received. The transition interval may end when the UE receives an acknowledgment that the eNB has received the RRCConnectionReconfigurationComplete message sent by the UE. The UE may send the RRCConnectionReconfigurationComplete message on the PUSCH to the eNB, and the eNB may send an ACK on a Physical HARQ Indicator Channel (PHICH) for a PUSCH transmission containing the message.
[00084] The start and end of the transition interval in the eNB may be different from the start and end of the transition interval in the UE, for example, due to the delay in sending and receiving the RRC messages for reconfiguration. In a project, additional protection of the start and end of the transition interval can be achieved by using timers. For example, the transition interval can be extended for both the eNB and the UE for some period of time after the successful transfer of the RRCConnectionReconfigurationComplete message. Other timers, such as a minimum timer, a maximum timer, or both, can also be used.
[00085] In a project, an eNB can send double grants, using both DCI formats with and without CIF during the transition interval. The eNB can generate a first grant based on a DCI format without CIF (eg DCI 1A, 0 or Z format), generate a second grant based on a DCI format with CIF (eg DCI format 1A', 0' or Z'), and send both concessions to the UE. The eNB may continue to send double grants whenever the UE is scheduled until the eNB is certain that an RRC reconfiguration message has reached the UE. The eNB may determine this based on (i) a Radio Link Control (RLC) ACK received for the RRC reconfiguration message or (ii) a complete RRC reconfiguration message received from the UE. This design can guarantee that the UE can receive at least one grant whenever the UE is scheduled for data transmission.
[00086] In a project, dual grants sent using DCI formats with and without CIF can point to the same resources for the PDSCH or PUSCH assigned to the UE. In this design, PDSCH / PUSCH resources are not wasted, and double grants only result in the use of additional PDCCH resources. In another design, concessions can be double for different PDSCH / PUSCH resources. In this design, the UE can use the PDSCH / PUSCH resources indicated by the grant received by the UE and cannot use the PDSCH / PUSCH resources indicated by the grant lost by the UE. However, the eNB may be able to determine which grants have been received by the UE, and therefore the configuration of the UE, based on (i) the particular PUSCH resources used by the UE for uplink data transmission or (ii) ) the particular PUCCH resources used by the UE to send ACK/NACK feedback for data transmission on the downlink.
[00087] The eNB can send double grants so that the UE does not perform additional blind decodings. In addition, the eNB may send schedulerless dual grants and/or search space restrictions imposed by some of the designs described above. However, additional PUCCH resources can be consumed to send double leases, which can impose additional bursts for the PDCCH during the transition interval. The use of additional PUCCH resources can have negligible overall impact as RRC reconfiguration can be infrequent and the transition interval can be relatively short.
[00088] The techniques described herein can be used to operate on any number of carriers with cross-carrier signaling. These carriers can have the same bandwidth or different bandwidths. DCI sizes can be associated with carrier bandwidth. However, if multiple carriers of different bandwidth have the same DCI sizes for some DCI formats, then zero or some other schemes can be used to differentiate the DCI formats for the different carriers for DCI sent over a given carrier. Cross-carrier signaling can then be performed implicitly without using CIF.
[00089] If zero padding is applied over DCI 1A format to one or more carriers, then this carrier(s) may also need restoration to DCI 1A format. In that case, the designs described above can be used to support restoration operation on each such carrier.
[00090] Figure 9 shows a block diagram of a project of a 900 message generator, which can be part of an eNB. Within message generator 900, a module 912 can receive RRC reconfiguration messages for a UE and can determine the operating state of the UE. For example, the module 912 can determine whether the UE is operating on one carrier or multiple carriers, whether cross-carrier (or CIF) signaling is enabled for the UE, the downlink transmission mode configured for the UE to each carrier, etc. The module 912 may receive an indication of a bearer on which DCI will be sent to the UE, which may be referred to as a DCI bearer. The module 912 may then provide an indication of whether cross-carrier signaling is enabled for the UE over the ICD carrier and the downlink transmission mode configured for the UE over the DCI carrier.
[00091] The module 914 can receive the indication of the DCI carrier, the indication of whether CIF is enabled for the UE, and the downlink transmission mode for the UE over the DCI carrier. The module 914 can provide a set of DCI formats supported by the UE over the DCI carrier. DCI supported formats can include DCI formats without CIF and DCI formats with CIF. A module 916 can receive the DCI bearer indication, the set of supported DCI formats, and a DCI message type to send to the UE and can provide a selected DCI format.
[00092] A message generator 918 can receive the DCI to send to the UE and the selected DCI format and can generate a PUCCH message based on the selected DCI format. Module 920 may receive the PUCCH message and an indication of the selected CCEs for use for the PUCCH and may generate a PUCCH transmission with the PUCCH message sent about the selected CCEs.
[00093] Figure 10 shows a block diagram of a design of a message detector 1000, which can be part of a UE. Within message detector 1000, a module 1012 can receive RC reset messages for the UE and can determine the operational status of the UE. For example, module 1012 can determine whether the UE is operating on one carrier or multiple carriers, whether cross-carrier (or CIF) signaling is enabled for the UE, the downlink transmission mode selected for the UE on each carrier, etc. Module 1012 may receive an indication of a carrier on which to detect DCI, which may be referred to as a DCI carrier. Module 1012 may provide an indication of whether cross-carrier signaling is enabled for the UE and the downlink transmission mode for the DCI carrier.
[00094] A module 1014 can receive the DCI carrier indication, the indication of whether CIF is enabled, and the downlink transmission mode for the DCI carrier and can provide a set of DCI formats supported on the DCI carrier. A module 1016 can receive the indication of the DCI carrier and the set of DCI formats and can determine a set of decoding candidates for the DCI carrier. Each decoding candidate can correspond to a unique combination of a particular PDCCH candidate and a particular DCI size. Decoding candidates can be dependent on which DCI formats are allowed for each PDCCH candidate over the DCI carrier, as described above. A module 1018 can decode received samples based on each of the decoding candidates provided by module 1016. Module 1018 can provide decoded PUCCH messages corresponding to valid decoding candidates.
[00095] Figure 11 shows a design of a 1100 process for receiving DCI in a wireless communication system. Process 1100 may be performed by a UE (as described below), or by some other entity. The UE may determine at least a first DCI format (e.g., the DCI formats without CIF) to monitor a first carrier (block 1112). The UE may monitor the at least one first DCI format on the first carrier to detect DCI sent to the UE (block 1114). The UE may receive a reconfiguration message related to communication on a plurality of carriers by the UE with the cross-carrier signaling (block 1116). The UE may determine at least one second DCI format (e.g. the DCI formats with CIF) to monitor the first carrier based on the reset message (block 1118). The UE may monitor the at least one first DCI format and the at least one second DCI format on the first carrier after receiving the reconfiguration message to detect DCI sent to the UE (block 1120).
[00096] In a design, each second DCI format may comprise a corresponding first DCI format and at least one additional field that supports cross-carrier signaling, for example, as shown in figure 4. In a design, the at least one additional field may comprise CIF, which may indicate a carrier on which a data transmission is scheduled. The at least one additional field may also include different and/or other fields to support cross-carrier signaling. In a project, the at least one first DCI format can have a first size, and the at least one second DCI format can have a second size that is different from the first size.
[00097] In a project, restore operation may be supported by certain DCI formats on the first carrier. In one design, the at least one prior DCI format may include DCI 1A format for downlink grants, or DCI 0 format for uplink grants, or some other DCI formats, or a combination of these. In one design, the at least one second DCI format may include DCI format 1A' comprising DCI format 1A and CIF, or DCI format 0' comprising DCI format 0 and CIF, or some other DCI formats , or a combination of these.
[00098] In a project, restore operation may be supported by a mode dependent DCI format. In another design, restore operation cannot be supported by a mode dependent DCI format. In this design, the UE can determine a third DCI format to monitor the first carrier before receiving the reset message. The UE may monitor the third format of DCI on the first carrier, before receiving the reconfiguration message, to detect DCI sent to the UE. The UE may determine a fourth DCI format to monitor the first carrier after receiving the reconfiguration message. The UE can monitor the fourth DCI format, but not the third DCI format with the first carrier, after receiving the reset message, to detect DCI sent to the UE. The third and fourth DCI formats can be associated with a transmission mode of the UE on the first carrier. For example, the third DCI format can be any of the DCI formats shown in Table 1, and the fourth DCI format can comprise the third DCI format and the CIF.
[00099] In one project, restore operation can be supported on all carriers. In another design, restore operation may be limited to one or more designated carriers. In this design, the UE can monitor the at least one first DCI format and the at least one second DCI format on a subset of the plurality of carriers after receiving the reset message. This subset can include the first carrier, which can be a primary carrier. The UE may monitor the at least one second DCI format, but not the at least one first DCI format over the remainder of the plurality of carriers after receiving the reconfiguration message.
[000100] In a project, restore operation can be supported by all search spaces on the first carrier. For block 1120, the UE may monitor the at least one second DCI format in all search spaces for the UE on the first carrier. In another design, restore operation can be limited to a subset of the search spaces for the UE on the first carrier. For block 1120, the UE can monitor the at least one second DCI format in a UE-specific search space, but not a common search space, for example, as shown in Table 3.
[000101] In a project, restore operation can be supported by all PDCCH candidates for the UE on the first carrier. The UE may determine a plurality of PDCCH candidates for the UE on the first carrier. The UE may decode the plurality of PDCCH candidates based on the at least one first DCI format and also the at least one second DCI format.
[000102] In another design, restore operation may be supported by a subset of the PDCCH candidates for the UE on the first carrier. The UE may determine a first set of PDCCH candidates and a second set of PDCCH candidates for the UE on the first carrier. The UE may decode the first set of PDCCH candidates into the at least one first DCI format, but not the at least one second DCI format. The UE may decode the second set of PDCCH candidates into the at least one first DCI format and the at least one second DCI format. In one design, the first set of PDCCH candidates can be for the common search space for the UE over the first carrier, and the second set of PDCCH candidates can be for the UE-specific search space for the UE over the first carrier as shown in Table 3. In another design, the first and second sets of PDCCH candidates may correspond to different parts of a search space for the UE on the first carrier. In yet another design, the first and second sets of PDCCH candidates may correspond to different parts of an aggregation level for a search space for the UE on the first carrier. The first and second sets of PDCCH candidates can also be defined in other ways.
[000103] In a project, a transition monitoring mode may be supported. The UE may determine a third DCI format (e.g., a mode dependent DCI format) to monitor the first carrier before receiving the reconfiguration message to detect DCI sent to the UE. The UE may monitor the at least one first DCI format and the at least one second DCI format, but not the third DCI format, on the first carrier during a transition interval for resetting the UE based on the reset message ( for example as shown in figure 8). The UE may determine the start of the transition interval based on the time the reconfiguration message is received by the UE. The UE may send a complete reconfiguration message to the base station and may then receive an acknowledgment for this message. The UE may determine the end of the transition interval based on (i) the time Tx when the complete reconfiguration message is sent by the UE or (ii) the time Ty when the acknowledgment for the complete reconfiguration message is received by the o EU. The UE can also determine the end of the transition interval on the additional basis of a timer, which can be started at time Tx or time Ty.
[000104] In a design, restore operation can be activated when a new carrier is added to the UE, eg as shown in figure 6. The UE can receive data (i) about a single carrier (eg the first carrier) before receiving the reconfiguration message and (ii) on the plurality of carriers with cross-carrier signaling after receiving the reconfiguration message. In one design, restore operation can be activated when cross-carrier (or CIF) signaling is activated, for example as shown in figure 7. The UE can receive data on the plurality of carriers (i) without cross-carrier signaling before receiving the reset message and (ii) with cross-carrier signaling after receiving the reset message.
[000105] Figure 12 shows a design of a process for sending 1200 DCI in a wireless communication system. Process 1200 can be performed by a base station / eNB (as described below), or by some other entity. The base station may determine at least a first DCI format monitored by a UE on a first carrier (block 1212). The base station may send DCI over the first carrier to the UE based on the at least one first DCI format (block 1214). The base station may send to the UE a reconfiguration message related to communication on a plurality of carriers by the UE with the cross-carrier signaling (block 1216). The base station may determine at least one second DCI format monitored by the UE on the first carrier in response to the reconfiguration message (block 1218). The base station may send DCI on the first carrier to the UE based on the at least one first DCI format and the at least one second DCI format after sending the reconfiguration message (block 1220). The first and second DCI formats can be as described above for figure 11.
[000106] In a project, restore operation may be supported by certain DCI formats (eg DCI Formats 1A and 0) on the first carrier. In a project, restore operation cannot be supported by a mode dependent DCI format. The base station may determine a third DCI format monitored by the UE on the first carrier before sending the reconfiguration message. The base station may send DCI on the first carrier to the UE based further on the third DCI format before sending the reconfiguration message. The base station may determine a fourth DCI format monitored by the UE on the first carrier after sending the reconfiguration message. The base station can send DCI on the first carrier to the UE based further on the fourth DCI format but not the third DCI format after sending the reconfiguration message. The third and fourth DCI formats can be associated with a transmission mode of the UE on the first carrier.
[000107] In one project, restore operation can be supported on all carriers. In another design, restore operation may be limited to one or more designated carriers. In this design, the base station can send DCI to the UE based on the at least one first DCI format and the at least one second DCI format on a subset of the plurality of carriers after sending the reset message. The base station may send DCI to the UE based on the at least one second DCI format, but not the at least one first DCI format over the remainder of the plurality of carriers after sending the reconfiguration message.
[000108] In one project, restore operation can be supported by all search spaces for the UE on the first carrier. In another design, restore operation can be limited to a subset of the search spaces for the UE on the first carrier. For example, the base station can send DCI to the UE based on at least a second DCI format in a UE-specific search space, but not a common search space for the UE over the first carrier, e.g. shown in Table 3.
[000109] In a project, restore operation can be supported by all PDCCH candidates for the UE on the first carrier. In another design, restore operation can be supported by a subset of the PDCCH candidates for the UE on the first carrier. By this design, the base station can send DCI based on the at least a first DCI format, but not on the at least a second DCI format a first set of PDCCH candidates for the UE on the first carrier. The base station may send DCI based on the at least one first DCI format and the at least one second DCI format in a second set of PDCCH candidates for the UE on the first carrier. The first and second sets of PDCCH candidates can be defined in various ways, as described above for Figure 11.
[000110] In one design, restore operation can be activated when a new carrier is added to the UE, for example as shown in figure 6. The base station can send data to the UE (i) on a single carrier before sending the reset message and (ii) on the plurality of carriers with cross-carrier signaling after sending the reset message. In one design, restoration operation can be activated when cross-carrier (or CIF) signaling is activated, for example, as shown in figure 7. The base station can send data to the UE about the plurality of carriers (i) without cross-carrier signaling before sending the reset message and (ii) with cross-carrier signaling after sending the reset message.
[000111] In a project, the base station can send dual assignments/grants. The base station may generate a first grant for a data transmission to the UE based on one of the at least a first DCI format. The base station may generate a second grant for transmitting data to the UE based on one of the at least one second DCI format. The base station may send the first and second grants to the UE, for example, in the same subframe.
[000112] Figure 13 shows a block diagram of a design of a base station / eNB 110 and a UE 120, which can be one of the base stations / eNBs and one of the UEs in figure 1. The base station 110 can be equipped with T antennas 1334a to 1334t, and UE 120 can be equipped with R antennas 1352a to 1352r, where in general T > 1 and R > 1.
[000113] At base station 110, a transmission processor 1320 may receive data from a data source 1312 to one or more UEs scheduled for downlink data transmission, processing (e.g., encoding and modulating) the data to each UE based on one or more modulation and coding systems selected for that UE, and providing data symbols for all UEs. Transmission processor 1320 may also process control information (e.g., grants, reset messages, etc.) and provide control symbols. Transmission processor 1320 may also generate reference symbols for the synchronization signals and reference signals. The transmit MIMO processor (TX) 1330 can precode the data symbols, the control symbols and/or the reference symbols (if applicable) and can provide T output symbol streams to T modulators (MOD) 1332a to 1332t. Each modulator 1332 can process its output symbol stream (eg, by OFDM, etc.) to obtain an output sample stream. Each modulator 1332 may further condition (e.g., downconvert, filter, amplify, and upconvert) its output sample stream and generate a downlink signal. T downlink signals from modulators 1332a to 1332t can be transmitted through T antennas 1334a to 1334t, respectively.
[000114] At UE 120, R antennas 1352a to 1352r can receive downlink signals from base station 110, and each antenna 1352 can provide a received signal to an associated demodulator (DEMOD) 1354. Each demodulator 1354 can condition ( eg filter, amplify, downconvert, and digitize) its received signal to obtain samples and can further process the samples (eg by OFDM, etc.) to obtain received symbols. A MIMO detector 1360 can obtain symbols received from all demodulators 1354, perform MIMO detection on the received symbols if any, and provide detected symbols. A receive processor 1370 can process (e.g., demodulate and decode) the detected symbols, provide decoded data to the UE 120 and to a data store 1372, and provide decoded control information to a controller/processor 1390.
[000115] In the uplink, at UE 120, data from a data source 1378, control information (e.g., ACK information, CQI information, etc.) from the controller/processor 1390, and signals from reference can be processed by a transmission processor 1380, precoded by a MIMO TX processor 1382 if applicable, further processed by modulators 1354a to 1354r, and transmitted to base station 110. At base station 110, the link signals Upstream from UE 120 may be received by antennas 1334, processed by demodulators 1332, detected by a MIMO detector 1336 if applicable, and further processed by a receive processor 1338 to retrieve the data and control information sent by UE 120. 1338 may provide the retrieved data to a data store 1339 and may provide the retrieved control information to the controller/processor 1340.
[000116] Controllers / processors 1340 and 1390 can direct the operation of base station 110 and UE 120, respectively. Processor 1320, processor 1340, and/or other processors and modules in base station 110 may execute or direct process 1200 in FIG. 12 and/or other processes for the techniques described herein. Processor 1370, processor 1390, and/or other processors and modules in UE 120 may execute or direct process 1100 in Fig. 11 and/or other processes for the techniques described herein. Memories 1342 and 1392 can store the data and program codes for base station 110 and UE 120, respectively. A scheduler 1344 may schedule the UE 120 and/or other UEs for data transmission in downlink and/or uplink. Processor 1320, processor 1340, scheduler 1344, and/or other processors and modules at base station 110 may implement module 900 in Figure 9. Processor 1370, processor 1390, and/or other processors and modules at UE 120 may implement module 1000 in figure 10.
[000117] In one configuration, the apparatus 120 for wireless communication may include means for determining at least a first DCI format for monitoring a first carrier on a UE, means for monitoring the at least a first DCI format on the first carrier for detecting DCI sent to the UE, means for receiving at the UE a reconfiguration message related to the communication of a plurality of carriers by the UE with cross-carrier signaling, means for determining at least a second DCI format for monitoring the first carrier at the UE with based on the reconfiguration message, and means for controlling the at least one first DCI format and the at least one second DCI format on the first carrier after receiving the reconfiguration message to detect DCI sent to the UE.
[000118] In one configuration, apparatus 110 for wireless communication may include means for determining at least a first format of DCI monitored by a UE over a first carrier, means for sending DCI over the first carrier to the UE based on the at least a first DCI format, means for sending to the UE a reconfiguration message related to communication of a plurality of carriers by the UE with cross-carrier signaling, means for determining at least one second DCI format monitored by the UE over the first carrier, in response to the reconfiguration message, and means for sending DCI over the first carrier to the UE based on the at least one first DCI format and the at least one second DCI format after sending the reconfiguration message.
[000119] In one aspect, the above means may be processor(s) 1320, 1338 and/or 1340 at base station 110 and/or processor(s) 1370, 1380 and/or 1390 at UE 120, which may be configured to perform the functions recited by the above means. In another aspect, the aforementioned means can be one or more modules or any device configured to perform the functions recited by the aforementioned means.
[000120] Those of skill in the art should understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description above may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination of them.
[000121] Those of skill would further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above, generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends on the particular application and design constraints imposed on the total system. Persons skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure.
[000122] The various illustrative logic blocks, modules and circuits described in connection with the disclosure herein can be implemented or realized with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate (FPGA) array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors together with a DSP core, or any other such configuration.
[000123] The steps of a method or algorithm described in connection with the disclosure here can be incorporated directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium can be integral with the processor. The processor and storage medium can reside on an ASIC. The ASIC can reside on a user terminal. Alternatively, the processor and storage medium can reside as discrete components in a user terminal.
[000124] In one or more exemplary projects, the described functions can be implemented in hardware, software, firmware, or any combination of these. If implemented in software, the functions can be stored or transmitted as one or more instructions or code in a computer-readable medium. Computer readable media includes both computer storage media and communication media including any media that facilitates the transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer. For purposes of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to transport or store desired program code media, in the form of instructions or data structures and which can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly called a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, so coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the medium definition. Disk and floppy disk, as used herein, include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, and blu-ray disks where floppy disks normally reproduce data magnetically, while disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.
[000125] The foregoing description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the inventive concept or scope of the invention. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but the broadest scope consistent with the principles and new features described herein should be granted.

权利要求:
Claims (8)
[0001]
1. Method for wireless communication, CHARACTERIZED by the fact that it comprises:- monitoring (1114), in a user equipment, UE (120), downlink control information, DCI, of a first carrier received by the UE (120 ), the monitoring being based on at least a first DCI format; - receiving (1116), at the UE (120), a reconfiguration message indicating a transition between downlink control signaling without cross-carrier signaling and control signaling downlink with cross-carrier signaling; - monitor (1120), in the UE (120), upon receipt of the reconfiguration message, the DCI of the first carrier based on at least one first DCI format and at least one second format DCI, monitoring including monitoring a first set of downlink channel elements received from the first carrier based on at least one DCI format and monitoring a second set of downlink channel elements ndent received from the first carrier based on at least one first DCI format and at least one second DCI format, wherein the first set of received downlink channel elements corresponds to a common search space on the first carrier, and wherein the second set of received downlink channel elements corresponds to a UE-specific search space on the first carrier.
[0002]
2. Method according to claim 1, CHARACTERIZED by the fact that the second DCI format is a DCI format that supports cross-carrier signaling and comprises a corresponding DCI format not supporting cross-carrier signaling and at least one additional field supporting signaling of cross-carrier.
[0003]
3. Method according to claim 2, CHARACTERIZED by the fact that at least one additional field comprises a cross-carrier indication field, CIF, indicating a carrier on which a data transmission is programmed.
[0004]
4. Method according to any one of claims 1 to 3, CHARACTERIZED by the fact that at least one first DCI format has a first size, and wherein the at least one second DCI format has a second size different from the first size.
[0005]
5. User equipment, UE (120), for wireless communication, CHARACTERIZED by the fact that it comprises:- mechanisms for monitoring downlink control information, DCI, on the first carrier received by the UE (120), monitoring including monitor a first set of downlink control channel elements received from the first carrier based on at least a first DCI format; mechanisms for receiving a reconfiguration message indicating a transition between downlink control signaling without carrier signaling cross-link and downlink control signaling with cross-carrier signaling;- mechanisms for monitoring, after receiving the reset message, the DCI on the first carrier based on at least a first DCI format and at least a second DCI format, the monitoring including monitoring the first set of downlink control channel elements received from the first by carrier based on at least a first DCI format and monitor a second set of downlink control channel elements received from the first carrier based on one of at least a first DCI format and at least one second DCI format, wherein the the first set of received downlink control channel elements corresponds to a common search space on the first carrier, and wherein the second set of received downlink control channel elements corresponds to a UE-specific search space on the first carrier.
[0006]
6. Method for wireless communication, CHARACTERIZED by the fact that it comprises:- sending (1214) downlink control information, DCI, of a first carrier to a user equipment (120), the sending being based on at least one first DCI format;- send (1216) to the UE (120) a reconfiguration message indicating a transition between downlink control signaling without cross-carrier signaling and downlink control signaling with cross-carrier signaling;- send (1220) to the UE (120) after sending the reset message, the DCI of the first carrier based on at least a first DCI format and at least a second DCI format, sending including sending a first set of channel elements first carrier downlink channel elements based on at least a first DCI format and send a second set of first carrier downlink channel elements based on at least one first DCI format and at least one second DCI format, wherein the first set of downlink channel elements corresponds to a common search space on the first carrier, and wherein the second set of downlink channel elements corresponds to a UE-specific search space in the first carrier.
[0007]
7. Apparatus for wireless communication, CHARACTERIZED by the fact that it comprises:- mechanisms for sending downlink control information, DCI, of a first carrier to a user equipment (120), the sending being based on at least a first DCI format;- mechanisms for sending to the UE (120) a reconfiguration message indicating a transition between downlink control signaling without cross-carrier signaling and downlink control signaling with cross-carrier signaling;- mechanisms for sending to the UE (120) after sending the reconfiguration message, the DCI of the first carrier based on at least a first DCI format and at least a second DCI format, sending including sending a first set of downlink channel elements of the first carrier based on at least a first DCI format and sending a second set of downlink channel elements of the first port now based on at least one first DCI format and at least one second DCI format, wherein the first set of downlink channel elements corresponds to a common search space on the first carrier, and wherein the second set of elements of downlink channel corresponds to a UE-specific search space on the first carrier.
[0008]
8. Memory CHARACTERIZED by the fact that it comprises instructions for causing at least one computer to perform the method as defined in any one of claims 1 to 4 or 6.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112012015950B1|2021-06-15|EMERGENCY OPERATION FOR CROSS CARRIER SIGNALING IN MULTI-CARRIER OPERATION

---

ES2773918T3|2020-07-15|Procedure for reporting channel status information on a wireless access system that supports unlicensed bands, and apparatus that supports the same

---

ES2875736T3|2021-11-11|Improved Blind Decoding Reduction in Carrier Aggregation

---

JP6293354B2|2018-03-14|Method and apparatus for system information block | acquisition for wireless transmit / receive unit | in non-CE mode and coverage extension | mode

---

EP3327975A1|2018-05-30|Downlink control information receiving method and user equipment, and downlink control information transmission method and base station

---

ES2745253T3|2020-02-28|Downlink coverage improvements

---

JP2016178695A|2016-10-06|Control channel allocation method, and apparatus for the same

---

US10749648B2|2020-08-18|Method and user equipment for receiving downlink signal, and method and base station for transmitting downlink signal

---

US10477578B2|2019-11-12|Uplink data transmission method and user equipment, and uplink data reception method and base station

---

US20180376497A1|2018-12-27|Control information reception method and user equipment, and control information transmission method and base station

---

BRPI1013964B1|2021-04-20|method on a base unit to transmit control information to a communication device, method on a communication device to determine control information and communication device to determine control information

---

KR101863922B1|2018-06-01|Apparatus and method of solving cce confusion

---

ES2868086T3|2021-10-21|Downlink control information set switching when using carrier aggregation.

---

US9807737B2|2017-10-31|Method for receiving control information in wireless communications system and apparatus therefor

---

BR112012006948B1|2021-04-27|METHOD FOR EXTENDING A REGION OF PDCCH AND EU DEVICE TO RECEIVE DCI INFORMATION

---

ES2894831T3|2022-02-16|Techniques for allocating the processing power of user equipment among multiple access nodes

---

KR20150079582A|2015-07-08|Method and apparatus for receiving control information in wireless communication system

---

US10201005B2|2019-02-05|Method for transmitting and receiving control channel and device therefor

---

KR20150079581A|2015-07-08|Method for receiving control information in wireless communication system and apparatus therefor

---

JP6727562B2|2020-07-22|Method and node in a wireless communication network

---

BRPI1007085B1|2021-01-19|method for managing communication of control channels for multiple carriers between a primary station and at least one secondary station, secondary station comprising device for multiple carriers for communication with a primary station and primary station for managing operation of control channels comprising device for multiple carriers to communicate with at least one secondary station

---

BR112020001618A2|2020-07-21|terminal and radio communication method for a terminal

---

BR112019018424A2|2020-04-14|high reliability and low latency configuration for wireless communications systems

---

BR112019019486A2|2020-04-22|data sending method, terminal device, and network device

---

US9401794B2|2016-07-26|Method and apparatus for acquiring control information in wireless communication system

同族专利:

---

公开号 | 公开日

---

EP2520039B1|2019-05-08|

---

BR112012015950A2|2019-11-12|

---

ES2739671T3|2020-02-03|

---

CN102687453B|2015-04-29|

---

WO2011090688A3|2012-03-01|

---

TW201136256A|2011-10-16|

---

CA2785649C|2016-01-19|

---

US9124406B2|2015-09-01|

---

RU2531596C2|2014-10-20|

---

JP5591950B2|2014-09-17|

---

RU2012132431A|2014-02-10|

---

JP2013516148A|2013-05-09|

---

CA2785649A1|2011-07-28|

---

HUE044913T2|2019-11-28|

---

KR101465507B1|2014-12-10|

---

CN102687453A|2012-09-19|

---

HK1176759A1|2013-08-02|

---

KR20120112686A|2012-10-11|

---

US20120009923A1|2012-01-12|

---

ZA201205382B|2018-11-28|

---

WO2011090688A2|2011-07-28|

---

EP2520039A2|2012-11-07|

---

BR112012015950A8|2019-12-03|

---

TWI459772B|2014-11-01|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

JP3875079B2|2001-11-16|2007-01-31|ソフトバンクテレコム株式会社|Orthogonal frequency division multiplexing system and transmitter / receiver|

---

JP3945325B2|2002-07-01|2007-07-18|ソニー株式会社|Wireless communication system, wireless communication apparatus, wireless communication method, and computer program|

---

US7889804B2|2003-05-30|2011-02-15|Mohammad Jaber Borran|Partially coherent constellations for multiple-antenna systems|

---

CN1830171B|2003-06-27|2010-05-05|诺基亚公司|Method and apparatus for packet aggregation in a wireless communication network|

---

JP2005045504A|2003-07-28|2005-02-17|Toshiba Corp|Multi-carrier communication system, multi-carrier receiving device, and multi-carrier transmitting device|

---

EP1719264B1|2003-10-07|2009-12-02|Telefonaktiebolaget LM Ericsson |Method and system of transmission power control|

---

FI20031582A0|2003-10-30|2003-10-30|Nokia Corp|Procedure for closed-loop power control in a communication system|

---

US7184792B2|2004-02-10|2007-02-27|Qualcomm Incorporated|Delayed data transmission in a wireless communication system after physical layer reconfiguration|

---

CN100574177C|2005-06-23|2009-12-23|上海原动力通信科技有限公司|The distribution method of multi-carrier HSDPA control channel and group data transmission method|

---

EP1944896A1|2007-01-09|2008-07-16|Matsushita Electric Industrial Co., Ltd.|Configuration of control channels in a mobile communication system|

---

US9344259B2|2007-06-20|2016-05-17|Google Technology Holdings LLC|Control channel provisioning and signaling|

---

US8446849B2|2007-06-20|2013-05-21|Qualcomm Incorporated|Methods and apparatuses for power control|

---

US20090163158A1|2007-08-07|2009-06-25|Interdigital Patent Holdings, Inc.|Support of downlink dual carriers and other features of evolved geran networks|

---

KR101448309B1|2007-09-28|2014-10-08|엘지전자 주식회사|Method of monitoring downlink control channel in wireless communication system|

---

RU2459384C2|2007-10-09|2012-08-20|Телефонактиеболагет Л М Эрикссон |Method to control upstream capacity in system of telecommunications network, which supports both general and separate tpc commands|

---

JP4555892B2|2007-10-29|2010-10-06|パナソニック株式会社|Mobile station apparatus, base station apparatus, control channel decoding method, and control channel allocation method|

---

KR101459147B1|2008-02-04|2014-11-10|엘지전자 주식회사|Method of transmitting transmit power control command in wireless communication system|

---

WO2009113934A1|2008-03-13|2009-09-17|Telefonaktiebolaget L M Ericsson |Methods and arrangements for uplink multicarrier power control in a wireless communications system|

---

KR100913473B1|2008-03-20|2009-08-25|엘지전자 주식회사|Method for monitoring pdcch in wireless communication|

---

WO2009134180A1|2008-04-28|2009-11-05|Telefonaktiebolaget L M Ericsson |Methods and arrangements for downlink multi-carrier power control in a wireless communications system|

---

US8295868B2|2008-06-09|2012-10-23|Samsung Electronics Co., Ltd.|Downlink control information format for multiple codeword transmission|

---

KR20100014091A|2008-08-01|2010-02-10|엘지전자 주식회사|Method of transmitting data in multiple carrier system|

---

KR101537614B1|2008-08-11|2015-07-22|엘지전자 주식회사|Method of signaling control information in wireless communication system with multiple frequency blocks|

---

KR101089838B1|2008-08-13|2011-12-05|한국전자통신연구원|Communication system of using carrier aggregation and base station and terminl included in the communication system|

---

US20100046412A1|2008-08-22|2010-02-25|Texas Instruments Incorporated|Reference signal structures for more than four antennas|

---

US8937913B2|2008-12-11|2015-01-20|Lg Electronics Inc.|Method for control channel detection in a multicarrier system|

---

KR101104965B1|2008-12-19|2012-01-12|한국전자통신연구원|Method and Apparatus for scheduling in BaseStation|

---

CN101465720B|2009-01-23|2013-08-21|中兴通讯股份有限公司|Method and device for sending upward HARQ feedback information|

---

US20130153298A1|2009-02-19|2013-06-20|Interdigital Patent Holdings, Inc.|Method and apparatus for enhancing cell-edge user performance and signaling radio link failure conditions via downlink cooperative component carriers|

---

US20100215011A1|2009-02-26|2010-08-26|Interdigital Patent Holdings, Inc.|Method and apparatus for switching a resource assignment mode for a plurality of component carriers|

---

KR20100100592A|2009-03-06|2010-09-15|삼성전자주식회사|Method and apparatus for power control in wireless communication system|

---

WO2010105148A1|2009-03-12|2010-09-16|Interdigital Patent Holdings, Inc.|Method and apparatus for monitoring for a radio link failure|

---

US20100254329A1|2009-03-13|2010-10-07|Interdigital Patent Holdings, Inc.|Uplink grant, downlink assignment and search space method and apparatus in carrier aggregation|

---

CN101505498B|2009-03-17|2014-02-05|中兴通讯股份有限公司|Downlink control information sending method, related system and apparatus|

---

US8437798B2|2009-04-27|2013-05-07|Motorola Mobility Llc|Uplink scheduling support in multi-carrier wireless communication systems|

---

WO2010124745A1|2009-04-30|2010-11-04|Telefonaktiebolaget L M Ericsson |Method and arrangement in a wireless communications system|

---

US9084206B2|2009-06-23|2015-07-14|Samsung Electronics Co., Ltd|Method and apparatus for controlling uplink transmission power in wireless communication system|

---

TWI444076B|2009-07-14|2014-07-01|Htc Corp|Method of handling random access procedure and related communication device|

---

US20110038331A1|2009-08-14|2011-02-17|Nokia Siemens Networks Oy|Control Channel Transmission With Component Carrier Aggregation|

---

JP5568747B2|2009-08-17|2014-08-13|パナソニックインテレクチュアルプロパティコーポレーションオブアメリカ|COMMUNICATION DEVICE, CONTROL INFORMATION ALLOCATION METHOD, AND INTEGRATED CIRCUIT|

---

US8194603B2|2009-08-18|2012-06-05|Motorola Mobility, Inc.|Subframe component reduction and notification in a heterogeneous wireless communication system|

---

US9351293B2|2009-09-11|2016-05-24|Qualcomm Incorporated|Multiple carrier indication and downlink control information interaction|

---

US8818441B2|2009-10-02|2014-08-26|Interdigital Patent Holdings, Inc.|Method and apparatus for controlling transmit power of transmissions on more than one component carrier|

---

US9763197B2|2009-10-05|2017-09-12|Qualcomm Incorporated|Component carrier power control in multi-carrier wireless network|

---

WO2011063244A2|2009-11-19|2011-05-26|Interdigital Patent Holdings, Inc.|Component carrier activation/deactivation in multi-carrier systems|

---

US8958841B2|2009-12-27|2015-02-17|Lg Electronics Inc.|Method and apparatus for controlling uplink transmission power in a multi-carrier wireless communication system|

---

EP2378821A3|2010-04-07|2012-03-21|HTC Corporation|Communication device and method thereof|

---

TW201206105A|2010-06-25|2012-02-01|Htc Corp|Method of handling downlink control information indication and related communication device|USRE34588E|1987-11-17|1994-04-19|Hong; Kuochih|Hydrogen storage hydride electrode materials|

---

US5006328A|1987-11-17|1991-04-09|Kuochih Hong|Method for preparing materials for hydrogen storage and for hydride electrode applications|

---

US5501917A|1994-01-28|1996-03-26|Hong; Kuochih|Hydrogen storage material and nickel hydride batteries using same|

---

US9344259B2|2007-06-20|2016-05-17|Google Technology Holdings LLC|Control channel provisioning and signaling|

---

WO2010104361A2|2009-03-12|2010-09-16|Lg Electronics Inc.|The method for switching opeeating carrier at a user equipment in wireless communication system|

---

US8934417B2|2009-03-16|2015-01-13|Google Technology Holdings LLC|Resource allocation in wireless communication systems|

---

US9351293B2|2009-09-11|2016-05-24|Qualcomm Incorporated|Multiple carrier indication and downlink control information interaction|

---

US9763197B2|2009-10-05|2017-09-12|Qualcomm Incorporated|Component carrier power control in multi-carrier wireless network|

---

KR101763596B1|2010-01-06|2017-08-01|엘지전자 주식회사|apparatus and method for transmitting data burst using cross-carrier scheduling in wireless communication system supporting multiple component carrier|

---

MX2012009276A|2010-02-11|2012-10-15|Huawei Tech Co Ltd|Method, base station, user equipment and system for physical downlink control channel signalling transmission and reception.|

---

CN105356976B|2010-02-15|2018-11-30|太阳专利信托公司|Base station apparatus and sending method|

---

US9306723B2|2010-02-20|2016-04-05|Google Technology Holdings LLC|Multi-carrier control signaling in wireless communication system|

---

KR101707691B1|2010-03-09|2017-02-17|엘지전자 주식회사|Method for communication of user equipment in a in multiple carrier system|

---

EP2549820B1|2010-03-17|2015-07-29|LG Electronics Inc.|Method and apparatus for performing cross-carrier scheduling for SPS|

---

WO2011125004A1|2010-04-07|2011-10-13|Koninklijke Philips Electronics N.V.|Method for communicating in a mobile network during a transitional configuration mode|

---

US9451598B2|2010-12-02|2016-09-20|Lg Electronics Inc.|Method and apparatus for transmitting channel status information in carrier aggregation system|

---

GB2486926B|2011-06-02|2013-10-23|Renesas Mobile Corp|Frequency hopping in license-exempt/shared bands|

---

CN102811495A|2011-06-02|2012-12-05|华为技术有限公司|Method, device and system for receiving and sending scheduling information|

---

US8675605B2|2011-06-02|2014-03-18|Broadcom Corporation|Frequency hopping in license-exempt/shared bands|

---

US9258086B2|2011-08-03|2016-02-09|Qualcomm Incorporated|Allocating physical hybrid ARQ indicator channelresources|

---

US8983391B2|2011-08-12|2015-03-17|Sharp Kabushiki Kaisha|Signaling power allocation parameters for uplink coordinated multipoint |

---

CN102958184B|2011-08-25|2017-02-22|华为技术有限公司|Method, device and system for downlink control channel transmission|

---

US9402264B2|2011-09-30|2016-07-26|Intel Corporation|Methods to transport internet traffic over multiple wireless networks simultaneously|

---

CN103096488B|2011-10-27|2015-07-08|华为技术有限公司|Method and device of multi-carrier scheduling|

---

CN103096453B|2011-10-31|2016-01-13|上海贝尔股份有限公司|The method and apparatus of synchronous eNB and subscriber equipment in transport mode translations process|

---

KR20130049573A|2011-11-04|2013-05-14|삼성전자주식회사|Method and apparatus for transmitting contol signal|

---

WO2013066122A1|2011-11-04|2013-05-10|엘지전자 주식회사|Method and apparatus for user equipment searching control channel in wireless communication system|

---

ES2728444T3|2011-11-14|2019-10-24|Samsung Electronics Co Ltd|Procedure for assigning reference signaling resources for transmission of control channel in wireless communication system|

---

US9432994B2|2012-03-09|2016-08-30|Lg Electronics Inc.|Method for transreceiving signals and apparatus for same|

---

WO2013141801A1|2012-03-19|2013-09-26|Telefonaktiebolaget L M Ericsson |Aggregation of resources in enhanced control channels|

---

US9338773B2|2012-03-26|2016-05-10|Qualcomm Incorporated|Common search space for EPDCCH in LTE|

---

EP2848056B1|2012-05-11|2016-05-18|Telefonaktiebolaget LM Ericsson |A method and apparatus for resource assignment during control channel ambiguity|

---

US8995375B2|2012-05-11|2015-03-31|Telefonaktiebolaget L M Ericsson |Method and apparatus for resource assignment during control channel ambiguity|

---

KR20140019718A|2012-08-06|2014-02-17|주식회사 케이티|Method for transiting control information of transmission/reception point, transmission/reception point thereof, method for mapping uplink control channel resource of terminal and terminal thereof|

---

US10033504B2|2012-09-06|2018-07-24|Samsung Electronics Co., Ltd.|Method and apparatus for communicating downlink control information in an asymmetric multicarrier communication network environment|

---

WO2014038830A1|2012-09-07|2014-03-13|Samsung Electronics Co., Ltd.|Method and system for signalling resource allocation information in an asymmetric multicarrier communication network|

---

KR20150090054A|2012-11-27|2015-08-05|엘지전자 주식회사|Method for monitoring downlink control channel in wireless communication system, and apparatus therefor|

---

US9635659B2|2013-01-03|2017-04-25|Qualcomm Incorporated|ENB PDCCH implementation to avoid ambiguous DCI information|

---

US9226211B2|2013-01-17|2015-12-29|Intel IP Corporation|Centralized partitioning of user devices in a heterogeneous wireless network|

---

KR102202333B1|2013-01-26|2021-01-13|엘지전자 주식회사|Method for receiving downlink control information by ue in wireless communication system, and apparatus for same|

---

WO2014183296A1|2013-05-17|2014-11-20|华为技术有限公司|Service data scrambling method, service data descrambling method, apparatus, and system|

---

US10034278B2|2013-05-21|2018-07-24|Telefonaktiebolaget L M Ericsson |Method and device for handling different DCI messages in a wireless network node of a cellular communication system providing multiple bandwidths|

---

WO2015060631A1|2013-10-25|2015-04-30|주식회사 케이티|Method and device for transmitting and receiving downlink control information|

---

KR101723268B1|2013-10-25|2017-04-06|주식회사 케이티|Methods for transmitting and receiving the downlink control information and Apparatuses thereof|

---

WO2015113226A1|2014-01-28|2015-08-06|Telefonaktiebolaget L M Ericsson |Network node, wireless device,respective method performed thereby for supporting wireless device operation in heterogeneous frequency bands|

---

US9591649B1|2014-09-29|2017-03-07|Sprint Spectrum L.P.|Method and system of reducing load on a downlink control channel|

---

EP3595388A1|2014-12-30|2020-01-15|Huawei Technologies Co., Ltd.|Control information transmission method and apparatus|

---

GB2592483B|2015-09-25|2022-01-05|Tcl Communication Ltd|Wireless communication system devices|

---

US10298375B2|2015-12-30|2019-05-21|Telefonaktiebolaget Lm Ericsson |System, method, and apparatus for selecting downlink control information format|

---

US10356811B2|2016-01-28|2019-07-16|Qualcomm Incorporated|Methods and apparatus for grant processing|

---

US10756868B2|2016-07-01|2020-08-25|Qualcomm Incorporated|Techniques for transmitting a physical uplink shared channel in an uplink pilot time slot|

---

US10231228B2|2016-09-23|2019-03-12|Mediatek Inc.|Methods of two-stage scheduling in downlink control channel|

---

KR20180068677A|2016-12-14|2018-06-22|삼성전자주식회사|Method and apparatus for transmitting and receiving downlink control channel in wirelss communication system|

---

WO2018174530A1|2017-03-23|2018-09-27|삼성전자 주식회사|Method and apparatus for uplink power control in wireless cellular communication system|

---

KR102309741B1|2017-03-23|2021-10-08|삼성전자 주식회사|Method and apparatus for power control of uplink transmission in wirelss cellular communication system|

---

KR102279483B1|2017-03-24|2021-07-20|삼성전자 주식회사|Method and apparatus for decoding of downlink control signal in wirelss communication system|

---

US10897753B2|2017-05-04|2021-01-19|Sharp Kabushiki Kaisha|Systems and methods for supporting multiple allocations in UL/DL grant for a 5G NR UE and gNB|

---

US10880913B2|2017-11-16|2020-12-29|Qualcomm Incorporated|Efficient data scheduling with supplemental uplink carrier|

---

US11109360B2|2018-02-05|2021-08-31|Apple Inc.|Channel configuration and DLUL configuration for NB-IoT-U system|

---

WO2019160486A1|2018-02-16|2019-08-22|Telefonaktiebolaget Lm Ericsson |Efficient control signaling using common search space|

---

KR20200078216A|2018-12-21|2020-07-01|삼성전자주식회사|Method and apparatus for transmitting and receiving physical downlink control channel based on dft-s-ofdm in wirelss communication system|

---

US11178658B2|2019-03-29|2021-11-16|Lg Electronics Inc.|Method and apparatus for transmitting and receiving control information for sidelink communication in wireless communication system|

---

US20210321440A1|2020-04-09|2021-10-14|Qualcomm Incorporated|Downlink control informationdesign for multi-component carrier scheduling|

---

WO2022025498A1|2020-07-30|2022-02-03|엘지전자 주식회사|Method for performing channel access procedure and device therefor|

法律状态:
2019-12-03| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|

---

2020-02-18| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|

---

2021-04-06| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|

---

2021-06-15| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 23/12/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF |

优先权:

---

申请号 | 申请日 | 专利标题

---

US29072409P| true| 2009-12-29|2009-12-29|

---

US61/290,724|2009-12-29|

---

US31364710P| true| 2010-03-12|2010-03-12|

---

US61/313,647|2010-03-12|

---

US12/976,818|US9124406B2|2009-12-29|2010-12-22|Fallback operation for cross-carrier signaling in multi-carrier operation|

---

US12/976,818|2010-12-22|

---

PCT/US2010/062053|WO2011090688A2|2009-12-29|2010-12-23|Fallback operation for cross-carrier signaling in multi-carrier operation|

---